Instructions on how to use testbed(for Ex4)

First the basic scenarios:
Enumerator creates 10 components(BSMonitor), we send Msg 41(BS Reading) through prjRemote to 10 created components, 10 components return Msg 42(Diagnosis with user profile),  Verifier checks the returned Msg 42 with KB to see if it's correct, Verifier send verification results to eliminator, eliminator gives decisions of component selection to SISServer when it reaches slow cycle or upon request by time controller, SISServer sends Msg 25(Deactivation) to eliminated components, eliminated components will no longer receive msgs unless it'd again activated.

Second actual run procedure and some specifications:
1. Run SISServer through scripts/runserver.bat
2. Run prjRemote.exe and connect
3. Load Initxmls for Eliminator, Verifier, SBSKB(i.e. CreateEliminator.xml, CreateVerifier.xml, CreateKB.xml under testbed/xml/InitXML)
4. Load InitXMLs for your own Enumerator, TimeController
5. Run Eliminator, Verifier, SBSKB through testbed/scripts/ runVerifier_Eliminator.bat and runKB.bat
6. Load InputBSK.xml under testbed/xml/DataXML and send, you can load multiple times and send with different data and diagnosis results
7. Run your own Enumerator and Enumerator start probably 10 components, Run your Time controller
8. Send multiple Msg 41(under testbed/xml/DataXML) with different data value(These values should be within KB(InputBSK.xml you have sent) so that verifier could check with KB)
9. Your parameterized component do the following job, receive Msg 41, return diagnosis Msg 42, display all input output msgs
The Msg 42 should be in the following format:
MsgID:42
Description:Blood Sugar Diagnosis
Sex:Male/Female
Age:
Weight:
Height:
Diabetes:
Heart Disease:
Meal:
Blood Sugar:
Diagnosis:normal/abnormal
Suggestion:
Name:
DateTime:

Note: values of the patient information attributes(e.g. Age, Weight, Meal ... ) in the Msg 42 should conform the KB's(InputBSK.xml) values so that verifier could track the correct diagnosis

10. Your Time Controller do the following job:
When interrupted, send Msg 310 to ask Eliminator to make instant decision even though Eliminator has not yet reached its built-in slow cycle, The format of Msg 310 are as follows:
MsgID: 310
Description: blabla
Type: BloodSugarMonitor

Note: the Type value(i.e. BloodSugarMonitor) must not be changed if you would like to use the provided verifier.
Note: The Eliminator's built in slow cycle is a counter of 15, when the diagnosis count reaches 15 for each active component, it does selection. The selection threashold is 0.7, meaning that components having correct rate greater than 0.7 could survive.

11. Test with your time controller after several rounds of diagnosis(Msg 42), you should find some of your components received Msg 25(Denoting deactivation), some others not.